Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c2475a2a7d89fe51456e72f5ff37443a4078dc82081e34c9fed7a124e6594bd

Tx prefix hash: 0888d5736315a95b1543619bf72d1c9738964e2dccffa59c06e9e0679c02f0bd
Tx public key: ca045fd80708b18206e9b7733f583e2ff3e15e681da98a4f77a28b9180c09fe3
Timestamp: 1713420476 Timestamp [UCT]: 2024-04-18 06:07:56 Age [y:d:h:m:s]: 00:304:10:07:58
Block: 1002987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217603 RingCT/type: yes/0
Extra: 01ca045fd80708b18206e9b7733f583e2ff3e15e681da98a4f77a28b9180c09fe302110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7acd183949d7c3d64bbb3007b3711ffa3d2fa451549bfebf771cbbfb55a930f 0.600000000000 1463517 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": 1002997, "vin": [ { "gen": { "height": 1002987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7acd183949d7c3d64bbb3007b3711ffa3d2fa451549bfebf771cbbfb55a930f" } } ], "extra": [ 1, 202, 4, 95, 216, 7, 8, 177, 130, 6, 233, 183, 115, 63, 88, 62, 47, 243, 225, 94, 104, 29, 169, 138, 79, 119, 162, 139, 145, 128, 192, 159, 227, 2, 17, 0, 0, 0, 11, 82, 212, 126, 148, 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