Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5240bd34356bb9f7706ea8dc5c0900a744b82049d28ddbca985595124059bfba

Tx prefix hash: 688f71d336d108bc501bea63a4833c88e362df25e626c23ad73bb43c438e49b9
Tx public key: e7ba6a7d70d46e90b6c015ec27bcb34a04e04f25fa118143a3dca34d6cb47661
Timestamp: 1727728839 Timestamp [UCT]: 2024-09-30 20:40:39 Age [y:d:h:m:s]: 00:022:09:38:04
Block: 1121640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16003 RingCT/type: yes/0
Extra: 01e7ba6a7d70d46e90b6c015ec27bcb34a04e04f25fa118143a3dca34d6cb4766102110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bd3e0f54bb5d49a4973adcf7dd45a2eb7dd47233a8287a0b184f3b180b4e04e 0.600000000000 1603943 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": 1121650, "vin": [ { "gen": { "height": 1121640 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bd3e0f54bb5d49a4973adcf7dd45a2eb7dd47233a8287a0b184f3b180b4e04e" } } ], "extra": [ 1, 231, 186, 106, 125, 112, 212, 110, 144, 182, 192, 21, 236, 39, 188, 179, 74, 4, 224, 79, 37, 250, 17, 129, 67, 163, 220, 163, 77, 108, 180, 118, 97, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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