Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36c05de6c217bea3947a422e6c1c581ab33969331d5c5fc98436c2f4a4ef678b

Tx prefix hash: e1e460364cfb1ade0d0102c424155483584e6d21ed409e7c09528121280b01f7
Tx public key: 5a56fd8ea359374990c31e42e9ccb7876ddae8ecb11a1803cc5189abf7f43262
Timestamp: 1732939073 Timestamp [UCT]: 2024-11-30 03:57:53 Age [y:d:h:m:s]: 00:199:22:28:42
Block: 1164737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142619 RingCT/type: yes/0
Extra: 015a56fd8ea359374990c31e42e9ccb7876ddae8ecb11a1803cc5189abf7f43262021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dae1549175a4eb63d4d9db787191699f8214a4e52ae2531c8f9204d4842a153e 0.600000000000 1650412 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": 1164747, "vin": [ { "gen": { "height": 1164737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dae1549175a4eb63d4d9db787191699f8214a4e52ae2531c8f9204d4842a153e" } } ], "extra": [ 1, 90, 86, 253, 142, 163, 89, 55, 73, 144, 195, 30, 66, 233, 204, 183, 135, 109, 218, 232, 236, 177, 26, 24, 3, 204, 81, 137, 171, 247, 244, 50, 98, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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