Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f537c5387dd2a32cea25937d833d817f339193adf12df625f538137b18602521

Tx prefix hash: b608a33050dd40d02ea1ccbdadef9c55e74f22e5749b588924cb5bccd05ab161
Tx public key: e2e603d4dbdb3ea7d45e805c2baf8b4751bb39488bf5ac8adc57239222c6dc6d
Timestamp: 1720360322 Timestamp [UCT]: 2024-07-07 13:52:02 Age [y:d:h:m:s]: 00:326:15:37:10
Block: 1060535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233444 RingCT/type: yes/0
Extra: 01e2e603d4dbdb3ea7d45e805c2baf8b4751bb39488bf5ac8adc57239222c6dc6d02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c95d034bf810f403656097bf9a33ffed59d80bb36b4d9ebf2568b68c2a3feca 0.600000000000 1531018 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": 1060545, "vin": [ { "gen": { "height": 1060535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c95d034bf810f403656097bf9a33ffed59d80bb36b4d9ebf2568b68c2a3feca" } } ], "extra": [ 1, 226, 230, 3, 212, 219, 219, 62, 167, 212, 94, 128, 92, 43, 175, 139, 71, 81, 187, 57, 72, 139, 245, 172, 138, 220, 87, 35, 146, 34, 198, 220, 109, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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