Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf473dea0ce4b9fb0eac62abebdff22fee385c1b7606adfd094979700e83336f

Tx prefix hash: 73aaeab130af08cb6d96409febabda084bb519f63dfcd196833ff2edbc8e9e96
Tx public key: b27365ea3928168e3ae07b3a1da2053b185ac780cfae47d71d829b813b4ca0b7
Timestamp: 1707225231 Timestamp [UCT]: 2024-02-06 13:13:51 Age [y:d:h:m:s]: 01:063:15:13:58
Block: 951632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306544 RingCT/type: yes/0
Extra: 01b27365ea3928168e3ae07b3a1da2053b185ac780cfae47d71d829b813b4ca0b702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11fcecb2d4d6fc3bf40279ac659c0be2c9e7b69b7b4dd4ba32e573e383b32788 0.600000000000 1410428 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": 951642, "vin": [ { "gen": { "height": 951632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11fcecb2d4d6fc3bf40279ac659c0be2c9e7b69b7b4dd4ba32e573e383b32788" } } ], "extra": [ 1, 178, 115, 101, 234, 57, 40, 22, 142, 58, 224, 123, 58, 29, 162, 5, 59, 24, 90, 199, 128, 207, 174, 71, 215, 29, 130, 155, 129, 59, 76, 160, 183, 2, 17, 0, 0, 0, 1, 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