Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb9bec43eb6b9b641f11e78f799adf097e6b918733c1d31b662ee15ef5dffb19

Tx prefix hash: 688424ce692c96fad4c72636279866c3c8ec6be225fda7656bb2f9ba1635a919
Tx public key: f62945ca1fbae33b9e24c2188ca1a45810090db0176c2860d1c47f40ee8bd49c
Timestamp: 1731098779 Timestamp [UCT]: 2024-11-08 20:46:19 Age [y:d:h:m:s]: 00:128:14:24:19
Block: 1149491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91743 RingCT/type: yes/0
Extra: 01f62945ca1fbae33b9e24c2188ca1a45810090db0176c2860d1c47f40ee8bd49c02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: edd417954f8c81b0b07e8182e062f208b221943a75aa9f3ec0f6d40520d98461 0.600000000000 1634584 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": 1149501, "vin": [ { "gen": { "height": 1149491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "edd417954f8c81b0b07e8182e062f208b221943a75aa9f3ec0f6d40520d98461" } } ], "extra": [ 1, 246, 41, 69, 202, 31, 186, 227, 59, 158, 36, 194, 24, 140, 161, 164, 88, 16, 9, 13, 176, 23, 108, 40, 96, 209, 196, 127, 64, 238, 139, 212, 156, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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