Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9a7e0c8666ed50ae78c929c4856578b4b4d4e61d79294343fa9300bf98fe0a3

Tx prefix hash: 01d08f12601217fec67c870b98c8451e728c96c7abf80af07be00f9ed308e168
Tx public key: 7bd28d09ba47a47368c69433be95e58f5cb0dc5bb25f10c4924edf968ae83ea5
Timestamp: 1707667719 Timestamp [UCT]: 2024-02-11 16:08:39 Age [y:d:h:m:s]: 01:282:12:38:51
Block: 955304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460707 RingCT/type: yes/0
Extra: 017bd28d09ba47a47368c69433be95e58f5cb0dc5bb25f10c4924edf968ae83ea502110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9018209f61f9069e265a1b5ecfe2af72796299f31a7ef1a32cb7a49226fbd11 0.600000000000 1414590 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": 955314, "vin": [ { "gen": { "height": 955304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9018209f61f9069e265a1b5ecfe2af72796299f31a7ef1a32cb7a49226fbd11" } } ], "extra": [ 1, 123, 210, 141, 9, 186, 71, 164, 115, 104, 198, 148, 51, 190, 149, 229, 143, 92, 176, 220, 91, 178, 95, 16, 196, 146, 78, 223, 150, 138, 232, 62, 165, 2, 17, 0, 0, 0, 7, 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