Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f634cacbd70e73ed3bb0cbb989db03d19b36934f7eef7fe9ae9054775c6c8e01

Tx prefix hash: 699ae20a375a9404abb48aaa5db64f71677d65ec986596b327303a61e9afdc30
Tx public key: 97dd916be92874198311adf39b972fb8dd4ef27be4aa9ade596e94c2e630e5fa
Timestamp: 1648376701 Timestamp [UCT]: 2022-03-27 10:25:01 Age [y:d:h:m:s]: 03:045:19:36:51
Block: 467410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 812984 RingCT/type: yes/0
Extra: 0197dd916be92874198311adf39b972fb8dd4ef27be4aa9ade596e94c2e630e5fa0211000000095eb576c5000000000000000000

1 output(s) for total of 17.349097677000 dcy

stealth address amount amount idx
00: 47e8c1cb3d4d9e259c5163b38c6948067b7b12542fb89ed821ebd0013ed4ee83 17.349097677000 885911 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": 467420, "vin": [ { "gen": { "height": 467410 } } ], "vout": [ { "amount": 17349097677, "target": { "key": "47e8c1cb3d4d9e259c5163b38c6948067b7b12542fb89ed821ebd0013ed4ee83" } } ], "extra": [ 1, 151, 221, 145, 107, 233, 40, 116, 25, 131, 17, 173, 243, 155, 151, 47, 184, 221, 78, 242, 123, 228, 170, 154, 222, 89, 110, 148, 194, 230, 48, 229, 250, 2, 17, 0, 0, 0, 9, 94, 181, 118, 197, 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