Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6838802414be99216bdeba33f7d6b0e223b49896e126f3fd8956c3b0a3f73770

Tx prefix hash: 7bda00429d991075c5053e576e53434e37a046ab2bca972a4a849dbad6447e26
Tx public key: 529dc41724cb47c21939e3bff7add6f146c760473d0a70248237281a143b0965
Timestamp: 1738960684 Timestamp [UCT]: 2025-02-07 20:38:04 Age [y:d:h:m:s]: 00:285:11:23:25
Block: 1214317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201789 RingCT/type: yes/0
Extra: 01529dc41724cb47c21939e3bff7add6f146c760473d0a70248237281a143b0965021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11d9385ac971a0cfd49e153a37c34fd973f125c36b1084e7dc8b5d5ad407bef9 0.600000000000 1701106 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": 1214327, "vin": [ { "gen": { "height": 1214317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11d9385ac971a0cfd49e153a37c34fd973f125c36b1084e7dc8b5d5ad407bef9" } } ], "extra": [ 1, 82, 157, 196, 23, 36, 203, 71, 194, 25, 57, 227, 191, 247, 173, 214, 241, 70, 199, 96, 71, 61, 10, 112, 36, 130, 55, 40, 26, 20, 59, 9, 101, 2, 17, 0, 0, 0, 1, 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