Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 215b008533bd4a3af08e411e7078b4c3ecd9f54b34fb4caed399542351c2b0ca

Tx prefix hash: 89449e67f583de5b61b746ee09af4883944ac66e8f12e6c663eb5588abc0fcd3
Tx public key: 1ab9a5f3e0d8a5d790c015ab3b3795318c3d15a7770d6666393921839173382a
Timestamp: 1699623162 Timestamp [UCT]: 2023-11-10 13:32:42 Age [y:d:h:m:s]: 01:140:06:29:27
Block: 888627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361434 RingCT/type: yes/0
Extra: 011ab9a5f3e0d8a5d790c015ab3b3795318c3d15a7770d6666393921839173382a02110000000733af99f4000000000000000000

1 output(s) for total of 0.697605446000 dcy

stealth address amount amount idx
00: 5fe26b2722070f59a2831c36a9b880bf47e88a0dc5a125ea930b77cd2bc91611 0.697605446000 1344580 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": 888637, "vin": [ { "gen": { "height": 888627 } } ], "vout": [ { "amount": 697605446, "target": { "key": "5fe26b2722070f59a2831c36a9b880bf47e88a0dc5a125ea930b77cd2bc91611" } } ], "extra": [ 1, 26, 185, 165, 243, 224, 216, 165, 215, 144, 192, 21, 171, 59, 55, 149, 49, 140, 61, 21, 167, 119, 13, 102, 102, 57, 57, 33, 131, 145, 115, 56, 42, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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