Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6736a26aa5bc2901c9f91050de1c7c4fffa9a57b67d797f54fdcacfd8576774

Tx prefix hash: 3e6df4a1baf26d477eda70840499473e6ff95ba9c4acd40e4ea4052cb741bc8e
Tx public key: 025e6553c404b4f34b0932240b608543ef1e6f6a3222a6bb5094641b97381334
Timestamp: 1713280573 Timestamp [UCT]: 2024-04-16 15:16:13 Age [y:d:h:m:s]: 00:283:08:03:05
Block: 1001830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202772 RingCT/type: yes/0
Extra: 01025e6553c404b4f34b0932240b608543ef1e6f6a3222a6bb5094641b973813340211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ba2de26a0cdfe0055f7c2afc8c1e5b1333d255958cac8c7b9288b0ee1c4702b 0.600000000000 1462342 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": 1001840, "vin": [ { "gen": { "height": 1001830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ba2de26a0cdfe0055f7c2afc8c1e5b1333d255958cac8c7b9288b0ee1c4702b" } } ], "extra": [ 1, 2, 94, 101, 83, 196, 4, 180, 243, 75, 9, 50, 36, 11, 96, 133, 67, 239, 30, 111, 106, 50, 34, 166, 187, 80, 148, 100, 27, 151, 56, 19, 52, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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