Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69241b49a15b8043e78440ed0167241624032f28454217fd1a72aed1c7528d73

Tx prefix hash: 7451659b15a59ba734e963c8a27dfff04821df357170a4e6c607fbba9ee81be2
Tx public key: a640f735faeab3811cdfc2fde98a7568de72c87127b93b2d2f8b2a6ecf873be1
Timestamp: 1662818777 Timestamp [UCT]: 2022-09-10 14:06:17 Age [y:d:h:m:s]: 02:155:20:42:53
Block: 584940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 632666 RingCT/type: yes/0
Extra: 01a640f735faeab3811cdfc2fde98a7568de72c87127b93b2d2f8b2a6ecf873be102110000000875e3f0e9000000000000000000

1 output(s) for total of 7.077030070000 dcy

stealth address amount amount idx
00: b211fbf28ca493b86b5fa3011bcc2efe9c455548f78c6f321a65661713b2a444 7.077030070000 1018878 of 0

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": 584950, "vin": [ { "gen": { "height": 584940 } } ], "vout": [ { "amount": 7077030070, "target": { "key": "b211fbf28ca493b86b5fa3011bcc2efe9c455548f78c6f321a65661713b2a444" } } ], "extra": [ 1, 166, 64, 247, 53, 250, 234, 179, 129, 28, 223, 194, 253, 233, 138, 117, 104, 222, 114, 200, 113, 39, 185, 59, 45, 47, 139, 42, 110, 207, 135, 59, 225, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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