Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42d53b0d9c21ec022bd038ccc642b713d9a4171a2bf223b46388388fb61cd0b3

Tx prefix hash: 272e4337743f6c9e5edc50dba1eea8d564f9b9ac55d823724edd197e8ae06c3e
Tx public key: a68136b932cb5da5918c27f5b3be84de5cf3450ce5e5e231dfc4ffb8ad37d218
Timestamp: 1696094862 Timestamp [UCT]: 2023-09-30 17:27:42 Age [y:d:h:m:s]: 02:064:09:40:44
Block: 859570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 565701 RingCT/type: yes/0
Extra: 01a68136b932cb5da5918c27f5b3be84de5cf3450ce5e5e231dfc4ffb8ad37d218021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.870738622000 dcy

stealth address amount amount idx
00: bab1abf6d9479729ecb418883481d00330e9523192700b1fd92d38c7539f4c50 0.870738622000 1313802 of 0

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": 859580, "vin": [ { "gen": { "height": 859570 } } ], "vout": [ { "amount": 870738622, "target": { "key": "bab1abf6d9479729ecb418883481d00330e9523192700b1fd92d38c7539f4c50" } } ], "extra": [ 1, 166, 129, 54, 185, 50, 203, 93, 165, 145, 140, 39, 245, 179, 190, 132, 222, 92, 243, 69, 12, 229, 229, 226, 49, 223, 196, 255, 184, 173, 55, 210, 24, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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