Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: ad1135dad8dd91c3f7eeb7a102a79811dac7687ee360ba096297e70ad61bec80

Tx prefix hash: c9c5496a1dc98cd54df0e986bf3c7748028ec9d8da7e19c348e356f6aa27d409
Tx public key: 0c3ae4eb1a4b4fec98bb05992fbf0f72f8b745d7f1ca85ea902cafefaefdd78a
Timestamp: 1721845892 Timestamp [UCT]: 2024-07-24 18:31:32 Age [y:d:h:m:s]: 01:107:20:10:04
Block: 1072850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335571 RingCT/type: yes/0
Extra: 010c3ae4eb1a4b4fec98bb05992fbf0f72f8b745d7f1ca85ea902cafefaefdd78a021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 057ec04c17c7bda48a58f04dd97da875655dbcc4db54d5d8da596eb80983440d 0.600000000000 1545347 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1072860, "vin": [ { "gen": { "height": 1072850 } } ], "vout": [ { "amount": 600000000, "target": { "key": "057ec04c17c7bda48a58f04dd97da875655dbcc4db54d5d8da596eb80983440d" } } ], "extra": [ 1, 12, 58, 228, 235, 26, 75, 79, 236, 152, 187, 5, 153, 47, 191, 15, 114, 248, 183, 69, 215, 241, 202, 133, 234, 144, 44, 175, 239, 174, 253, 215, 138, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8