Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f23eb6fbb204d221b993ac7eb49c07144669074bc0f253ec41d36f92ebb44d27

Tx prefix hash: 2b848ee456356eb52580f101217747de011f041f205cb50807aeaa7a1c436e2c
Tx public key: b028817089ffde8da6f969f5e301c4c273d84ce7ce95a23c5d1f703041e0eeae
Timestamp: 1712916843 Timestamp [UCT]: 2024-04-12 10:14:03 Age [y:d:h:m:s]: 01:013:16:56:40
Block: 998806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270775 RingCT/type: yes/0
Extra: 01b028817089ffde8da6f969f5e301c4c273d84ce7ce95a23c5d1f703041e0eeae02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3e25815f5930a3c18280be31f6d45a9d6060c8a71b1d4a3c86ed06447109c02 0.600000000000 1459266 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": 998816, "vin": [ { "gen": { "height": 998806 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3e25815f5930a3c18280be31f6d45a9d6060c8a71b1d4a3c86ed06447109c02" } } ], "extra": [ 1, 176, 40, 129, 112, 137, 255, 222, 141, 166, 249, 105, 245, 227, 1, 196, 194, 115, 216, 76, 231, 206, 149, 162, 60, 93, 31, 112, 48, 65, 224, 238, 174, 2, 17, 0, 0, 0, 8, 82, 212, 126, 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