Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cafa3cd6d2e384049899653e20e69f9f9967ace179f00161cdcab2b90cbcb3c

Tx prefix hash: 932c24a41e317b52702c051903cda3fcb959df68337c3134add5532abb98db3e
Tx public key: 0a70963d13e5c7970735ea1e093a3a072cdb4efda0c0cc057a52f5801b4e2a4b
Timestamp: 1710387241 Timestamp [UCT]: 2024-03-14 03:34:01 Age [y:d:h:m:s]: 01:020:14:06:58
Block: 977881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275678 RingCT/type: yes/0
Extra: 010a70963d13e5c7970735ea1e093a3a072cdb4efda0c0cc057a52f5801b4e2a4b0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e3f0a9af649ee76a979c9b88067c79c63852d98b51a21d4c45c376163b9ad9e 0.600000000000 1437888 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": 977891, "vin": [ { "gen": { "height": 977881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e3f0a9af649ee76a979c9b88067c79c63852d98b51a21d4c45c376163b9ad9e" } } ], "extra": [ 1, 10, 112, 150, 61, 19, 229, 199, 151, 7, 53, 234, 30, 9, 58, 58, 7, 44, 219, 78, 253, 160, 192, 204, 5, 122, 82, 245, 128, 27, 78, 42, 75, 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