Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3dac2fbd814f51c22fe2d13d45d884b1a26b44f7cf78b426d07de3cdc4aee9ba

Tx prefix hash: 321f125ee39f536fc3f3dac02f1310c12209f21128fb7a348c3f1317058567ac
Tx public key: dd44b33ec3cc1708e70b36a0ecd9c1d417c472db7a67391ad814605d5de64bf9
Timestamp: 1740890638 Timestamp [UCT]: 2025-03-02 04:43:58 Age [y:d:h:m:s]: 00:303:23:02:57
Block: 1230278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215062 RingCT/type: yes/0
Extra: 01dd44b33ec3cc1708e70b36a0ecd9c1d417c472db7a67391ad814605d5de64bf9021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f0d1900aedd1b494a915e8965b8b639f1de273c41e4ecf0b71419e09354b948 0.600000000000 1717175 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": 1230288, "vin": [ { "gen": { "height": 1230278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f0d1900aedd1b494a915e8965b8b639f1de273c41e4ecf0b71419e09354b948" } } ], "extra": [ 1, 221, 68, 179, 62, 195, 204, 23, 8, 231, 11, 54, 160, 236, 217, 193, 212, 23, 196, 114, 219, 122, 103, 57, 26, 216, 20, 96, 93, 93, 230, 75, 249, 2, 17, 0, 0, 0, 4, 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