Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7619da0771bcf2b7d440bd82c88aed1c7fa84c587fd897fe81741ad105e5d659

Tx prefix hash: 1208de3c496e592a038e90a89c2b736149ab2a5ba3f980215ed5ee20c96e6289
Tx public key: b7210f3e8bf04823a745e96e2e0740e52e9398fbafc11fe80997b932d7027c5f
Timestamp: 1728101733 Timestamp [UCT]: 2024-10-05 04:15:33 Age [y:d:h:m:s]: 00:209:01:38:18
Block: 1124723 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149231 RingCT/type: yes/0
Extra: 01b7210f3e8bf04823a745e96e2e0740e52e9398fbafc11fe80997b932d7027c5f02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3194270c6724e71633897706e2e6ebaa7008d7204254ac631e2d5a9c8723f4c0 0.600000000000 1607388 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": 1124733, "vin": [ { "gen": { "height": 1124723 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3194270c6724e71633897706e2e6ebaa7008d7204254ac631e2d5a9c8723f4c0" } } ], "extra": [ 1, 183, 33, 15, 62, 139, 240, 72, 35, 167, 69, 233, 110, 46, 7, 64, 229, 46, 147, 152, 251, 175, 193, 31, 232, 9, 151, 185, 50, 215, 2, 124, 95, 2, 17, 0, 0, 0, 7, 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