Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5222e46f8d954d040c875f2eec0ac0941f0476272488488e25f0b1daffd8857c

Tx prefix hash: 83dfa5605df2231c2e483633d58741ea3aa71a7338b05175f355b20699cc9fb3
Tx public key: ac32de7ce0e4ce1bd7ec36098b8c9a875edad4cab6b141f1cd9395b611389131
Timestamp: 1673213850 Timestamp [UCT]: 2023-01-08 21:37:30 Age [y:d:h:m:s]: 02:070:20:15:33
Block: 670526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 572337 RingCT/type: yes/0
Extra: 01ac32de7ce0e4ce1bd7ec36098b8c9a875edad4cab6b141f1cd9395b61138913102110000000152542ceb000000000000000000

1 output(s) for total of 3.683570361000 dcy

stealth address amount amount idx
00: 973e4ea56da07e8e768657945fe8db78eb64a6a52f1bd25d00e51092b953e8aa 3.683570361000 1111937 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": 670536, "vin": [ { "gen": { "height": 670526 } } ], "vout": [ { "amount": 3683570361, "target": { "key": "973e4ea56da07e8e768657945fe8db78eb64a6a52f1bd25d00e51092b953e8aa" } } ], "extra": [ 1, 172, 50, 222, 124, 224, 228, 206, 27, 215, 236, 54, 9, 139, 140, 154, 135, 94, 218, 212, 202, 182, 177, 65, 241, 205, 147, 149, 182, 17, 56, 145, 49, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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