Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9777ad5c21895910a617c0b6b351be754d29c236c39aa19f2e4e2e69a9931b6

Tx prefix hash: 23689db3f9cc71ea46a0df96108ab660e0dd016b262bea0e39a3fcf8390e6ff0
Tx public key: 5ce1355ffdccbe42514e0f0cc288d0e020a526560c525e8481374be80301be1a
Timestamp: 1733408172 Timestamp [UCT]: 2024-12-05 14:16:12 Age [y:d:h:m:s]: 00:114:06:42:40
Block: 1168614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81474 RingCT/type: yes/0
Extra: 015ce1355ffdccbe42514e0f0cc288d0e020a526560c525e8481374be80301be1a021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4600da25a36b4bccf00d54fe019eb0f0e6df3d988511c0cae7c3e998d938027e 0.600000000000 1654325 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": 1168624, "vin": [ { "gen": { "height": 1168614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4600da25a36b4bccf00d54fe019eb0f0e6df3d988511c0cae7c3e998d938027e" } } ], "extra": [ 1, 92, 225, 53, 95, 253, 204, 190, 66, 81, 78, 15, 12, 194, 136, 208, 224, 32, 165, 38, 86, 12, 82, 94, 132, 129, 55, 75, 232, 3, 1, 190, 26, 2, 17, 0, 0, 0, 5, 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