Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 539ca525a49a67e8de1112cd3600478eba1022066d6c314811402d4c55372dcf

Tx prefix hash: afd4cf5eeab82004ced296c5d39fbac5df77e26444e273a3c13a1dea30cf582f
Tx public key: eec55ed28a7696a1a97a3ee9182e2b76a2298ba83f9c9c95dc0bf92982539f22
Timestamp: 1648413708 Timestamp [UCT]: 2022-03-27 20:41:48 Age [y:d:h:m:s]: 02:358:02:55:34
Block: 467744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 775293 RingCT/type: yes/0
Extra: 01eec55ed28a7696a1a97a3ee9182e2b76a2298ba83f9c9c95dc0bf92982539f2202110000000406faf294000000000000000000

1 output(s) for total of 17.306294509000 dcy

stealth address amount amount idx
00: 0a87168f2d34b33617783f8ab9fb78d8337ee537aa1fdaee227a1bd3c014abab 17.306294509000 886311 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": 467754, "vin": [ { "gen": { "height": 467744 } } ], "vout": [ { "amount": 17306294509, "target": { "key": "0a87168f2d34b33617783f8ab9fb78d8337ee537aa1fdaee227a1bd3c014abab" } } ], "extra": [ 1, 238, 197, 94, 210, 138, 118, 150, 161, 169, 122, 62, 233, 24, 46, 43, 118, 162, 41, 139, 168, 63, 156, 156, 149, 220, 11, 249, 41, 130, 83, 159, 34, 2, 17, 0, 0, 0, 4, 6, 250, 242, 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