Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e5420f9ffcc7dfbc9d97381df35b8d7671fd9b575a436114a80e4162f46a9d7

Tx prefix hash: 4aabd41fca86b53dcea8ae1e65abeb28d4d36da57780787e9d68975ee52b93c0
Tx public key: 078c003475d3e4b29fcd9da0f1d82f8facb45270021480fea075d898ea5a0e66
Timestamp: 1721475857 Timestamp [UCT]: 2024-07-20 11:44:17 Age [y:d:h:m:s]: 00:126:16:41:33
Block: 1069787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90658 RingCT/type: yes/0
Extra: 01078c003475d3e4b29fcd9da0f1d82f8facb45270021480fea075d898ea5a0e6602110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5dacf7bea11bfebc551bb51033ddac81a6da866b115c50b8ba9c103baa12e13 0.600000000000 1541356 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": 1069797, "vin": [ { "gen": { "height": 1069787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5dacf7bea11bfebc551bb51033ddac81a6da866b115c50b8ba9c103baa12e13" } } ], "extra": [ 1, 7, 140, 0, 52, 117, 211, 228, 178, 159, 205, 157, 160, 241, 216, 47, 143, 172, 180, 82, 112, 2, 20, 128, 254, 160, 117, 216, 152, 234, 90, 14, 102, 2, 17, 0, 0, 0, 3, 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