Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a87e9457c03055e64b846c63cee540f9020498b2a80bd593aa859164b1eaa844

Tx prefix hash: 471e4e8e5eb5f6a16c56894701d9ab3f375c61182934c5ac47bc6d6000c55413
Tx public key: 53dcacdb42f65804bcc851530c8385ec17ea7e05d8bf911965c2ea1b6f864e9b
Timestamp: 1732951044 Timestamp [UCT]: 2024-11-30 07:17:24 Age [y:d:h:m:s]: 00:123:05:43:51
Block: 1164826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87892 RingCT/type: yes/0
Extra: 0153dcacdb42f65804bcc851530c8385ec17ea7e05d8bf911965c2ea1b6f864e9b021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b37ac74a68530bb01563d33ec443cb3909d25b2da08a4c6344a1ae7aa3283593 0.600000000000 1650501 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": 1164836, "vin": [ { "gen": { "height": 1164826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b37ac74a68530bb01563d33ec443cb3909d25b2da08a4c6344a1ae7aa3283593" } } ], "extra": [ 1, 83, 220, 172, 219, 66, 246, 88, 4, 188, 200, 81, 83, 12, 131, 133, 236, 23, 234, 126, 5, 216, 191, 145, 25, 101, 194, 234, 27, 111, 134, 78, 155, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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