Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb9c310b288f2bfcc5afc5d06aebd2e6839c552090381bb75068a2f01a96f934

Tx prefix hash: ff04b799048eee346ea1f4320b42d2d9f2185be939130032f920a774d5d5e5cf
Tx public key: c6cf8bf91f30c5bfd1e7916356a27978b686ad0b8fa99700c4d91fb1a0c958e3
Timestamp: 1718915429 Timestamp [UCT]: 2024-06-20 20:30:29 Age [y:d:h:m:s]: 00:287:20:04:10
Block: 1048557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205691 RingCT/type: yes/0
Extra: 01c6cf8bf91f30c5bfd1e7916356a27978b686ad0b8fa99700c4d91fb1a0c958e302110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 389dd2685d00ab1134abe6ec7af18d92afadcbf911fff48c6fb903415fc4f466 0.600000000000 1518642 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": 1048567, "vin": [ { "gen": { "height": 1048557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "389dd2685d00ab1134abe6ec7af18d92afadcbf911fff48c6fb903415fc4f466" } } ], "extra": [ 1, 198, 207, 139, 249, 31, 48, 197, 191, 209, 231, 145, 99, 86, 162, 121, 120, 182, 134, 173, 11, 143, 169, 151, 0, 196, 217, 31, 177, 160, 201, 88, 227, 2, 17, 0, 0, 0, 3, 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