Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bebb89bf06894327da254e120fbfd2a90667f3a1236cb29d17dd41aba7b8e70

Tx prefix hash: 2b1b66f726ecd739e0cdfd91ab7aa5acef79cd0ce43526cac092ef8114fdb029
Tx public key: 506fd52dc2f4c0d22cfccf319369e53d378d0722d2febadd1d5a17c1f401d3e4
Timestamp: 1713336223 Timestamp [UCT]: 2024-04-17 06:43:43 Age [y:d:h:m:s]: 01:061:19:50:26
Block: 1002300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305056 RingCT/type: yes/0
Extra: 01506fd52dc2f4c0d22cfccf319369e53d378d0722d2febadd1d5a17c1f401d3e402110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd0f8ae2fe41cdc33160a51a990c61d417640cf749de82b6942acfd5c33a7a47 0.600000000000 1462816 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": 1002310, "vin": [ { "gen": { "height": 1002300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd0f8ae2fe41cdc33160a51a990c61d417640cf749de82b6942acfd5c33a7a47" } } ], "extra": [ 1, 80, 111, 213, 45, 194, 244, 192, 210, 44, 252, 207, 49, 147, 105, 229, 61, 55, 141, 7, 34, 210, 254, 186, 221, 29, 90, 23, 193, 244, 1, 211, 228, 2, 17, 0, 0, 0, 5, 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