Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c796d294594d5ca1526e64addd5b88e6a10dc8fdd6b5e02caf2a19cdfa528c78

Tx prefix hash: 3589ebb60eb864c3c6be2702460826e3dd4dea772cf5679f700f53880f9e7ab7
Tx public key: 59ab2fea8cfd39208a63588fc55d6efe9a3204f3340589eb0a85a6c41ba6fbc9
Timestamp: 1710322967 Timestamp [UCT]: 2024-03-13 09:42:47 Age [y:d:h:m:s]: 01:020:12:04:16
Block: 977339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275622 RingCT/type: yes/0
Extra: 0159ab2fea8cfd39208a63588fc55d6efe9a3204f3340589eb0a85a6c41ba6fbc90211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10b00f02e3887b0c4a80c9166421a5dc02dafbca02fcaa9f9a25fafa358a4330 0.600000000000 1437342 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": 977349, "vin": [ { "gen": { "height": 977339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10b00f02e3887b0c4a80c9166421a5dc02dafbca02fcaa9f9a25fafa358a4330" } } ], "extra": [ 1, 89, 171, 47, 234, 140, 253, 57, 32, 138, 99, 88, 143, 197, 93, 110, 254, 154, 50, 4, 243, 52, 5, 137, 235, 10, 133, 166, 196, 27, 166, 251, 201, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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