Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 391e93a8b43c80421e6e29bbd984e51919f573de75640a9552c8a3063025bcda

Tx prefix hash: 596c9a210420e59f90ee31b99da229b4ae0c36f7b88c6b451b78e84ee135e606
Tx public key: b197e3eff06c96a6d1c4279b190ae2af085fabe7df3bdf3337a485e147a37d06
Timestamp: 1707488252 Timestamp [UCT]: 2024-02-09 14:17:32 Age [y:d:h:m:s]: 01:113:00:44:26
Block: 953822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341883 RingCT/type: yes/0
Extra: 01b197e3eff06c96a6d1c4279b190ae2af085fabe7df3bdf3337a485e147a37d0602110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f94b74547b6e51b4f41c4dcaa4a2d5e95384391a7fb4c794071d12866cea49ed 0.600000000000 1413082 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": 953832, "vin": [ { "gen": { "height": 953822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f94b74547b6e51b4f41c4dcaa4a2d5e95384391a7fb4c794071d12866cea49ed" } } ], "extra": [ 1, 177, 151, 227, 239, 240, 108, 150, 166, 209, 196, 39, 155, 25, 10, 226, 175, 8, 95, 171, 231, 223, 59, 223, 51, 55, 164, 133, 225, 71, 163, 125, 6, 2, 17, 0, 0, 0, 4, 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