Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c4ed48f0eaeec5154564ab3d659e3e8896975e1e484fa4c68c72d2e98234a69

Tx prefix hash: fd7267777e3934547f6c1dab0876b9b8a61db2aa1d1ea59c3f28c3e50e47c358
Tx public key: 2a2e8778f21e1045b8d893f766a88328cf572ddf9c99b6d7c24f7826d6fbd783
Timestamp: 1710669997 Timestamp [UCT]: 2024-03-17 10:06:37 Age [y:d:h:m:s]: 00:313:13:38:40
Block: 980223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224393 RingCT/type: yes/0
Extra: 012a2e8778f21e1045b8d893f766a88328cf572ddf9c99b6d7c24f7826d6fbd78302110000001359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 305614fc686d58da6c637244260eee70e9422924ff4c8aad926ed55be88517c3 0.600000000000 1440288 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": 980233, "vin": [ { "gen": { "height": 980223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "305614fc686d58da6c637244260eee70e9422924ff4c8aad926ed55be88517c3" } } ], "extra": [ 1, 42, 46, 135, 120, 242, 30, 16, 69, 184, 216, 147, 247, 102, 168, 131, 40, 207, 87, 45, 223, 156, 153, 182, 215, 194, 79, 120, 38, 214, 251, 215, 131, 2, 17, 0, 0, 0, 19, 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