Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc31aa1dc21fc754b07637468078a62dc08415f51c51a5677d819e17547de0a4

Tx prefix hash: 873d90c619a31e785572d8e934c9c9a77be5f1d5c91997e62b0b0eaa9438cd6d
Tx public key: 55b5e8d3e29f8f6bc82fa21167b44775d38b78ecd07b28ad81839df213c37221
Timestamp: 1731771593 Timestamp [UCT]: 2024-11-16 15:39:53 Age [y:d:h:m:s]: 00:124:13:18:37
Block: 1155043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88860 RingCT/type: yes/0
Extra: 0155b5e8d3e29f8f6bc82fa21167b44775d38b78ecd07b28ad81839df213c3722102110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b05bebcc769afd1f60452bcf8a710e7554f95d39eabd4b968020bfc1f5ba85f7 0.600000000000 1640656 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": 1155053, "vin": [ { "gen": { "height": 1155043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b05bebcc769afd1f60452bcf8a710e7554f95d39eabd4b968020bfc1f5ba85f7" } } ], "extra": [ 1, 85, 181, 232, 211, 226, 159, 143, 107, 200, 47, 162, 17, 103, 180, 71, 117, 211, 139, 120, 236, 208, 123, 40, 173, 129, 131, 157, 242, 19, 195, 114, 33, 2, 17, 0, 0, 0, 12, 31, 10, 83, 235, 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