Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbd172ed70bc5977f1ae2cb4dd0dd8463f81d320d110e885033ac6c73d239d48

Tx prefix hash: 7b8207bc9bfe45c54e4f22f768b3f111199b21f0b6191e26cfb3df03728e49bc
Tx public key: ef81f530e8d1a3405b75092c0064da4f746c6ea71cb40f9422ba1787f38ac463
Timestamp: 1714253700 Timestamp [UCT]: 2024-04-27 21:35:00 Age [y:d:h:m:s]: 01:038:23:56:14
Block: 1009912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288837 RingCT/type: yes/0
Extra: 01ef81f530e8d1a3405b75092c0064da4f746c6ea71cb40f9422ba1787f38ac4630211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65f3adda40104292d41152322ed51d121f8c08efbea850fc91d4d735c1a5f7a8 0.600000000000 1471718 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": 1009922, "vin": [ { "gen": { "height": 1009912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65f3adda40104292d41152322ed51d121f8c08efbea850fc91d4d735c1a5f7a8" } } ], "extra": [ 1, 239, 129, 245, 48, 232, 209, 163, 64, 91, 117, 9, 44, 0, 100, 218, 79, 116, 108, 110, 167, 28, 180, 15, 148, 34, 186, 23, 135, 243, 138, 196, 99, 2, 17, 0, 0, 0, 5, 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