Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33ef311736b33a51b9594c7540032f4bdcaa8cb4a37fdd8a8f76f080ae1cce41

Tx prefix hash: 13292940412e9eb0e1ab2b1ae43e3e5550e3473cbb38c6f2b881367aab808554
Tx public key: dd49ecc2bc9709d1e4d7b3be35d0f636b664f00e4ffcb9cc751bc19fc12b0941
Timestamp: 1717362021 Timestamp [UCT]: 2024-06-02 21:00:21 Age [y:d:h:m:s]: 00:285:17:52:33
Block: 1035688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204227 RingCT/type: yes/0
Extra: 01dd49ecc2bc9709d1e4d7b3be35d0f636b664f00e4ffcb9cc751bc19fc12b094102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: faf276944c3a9152b6602a658bda828c2c802706d58a27f7e1ba5478d35b0e93 0.600000000000 1504211 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": 1035698, "vin": [ { "gen": { "height": 1035688 } } ], "vout": [ { "amount": 600000000, "target": { "key": "faf276944c3a9152b6602a658bda828c2c802706d58a27f7e1ba5478d35b0e93" } } ], "extra": [ 1, 221, 73, 236, 194, 188, 151, 9, 209, 228, 215, 179, 190, 53, 208, 246, 54, 182, 100, 240, 14, 79, 252, 185, 204, 117, 27, 193, 159, 193, 43, 9, 65, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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