Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a27847fbc6c1fe67c49a40ff0131226f2093d8ea93b4bf78908da16bfaa6e09e

Tx prefix hash: a0f89a78f70eadeea74a4a102d3cdccfae319fa26f39701451e571e47b91fd50
Tx public key: 6ebdaaf0fedb6686c3a0d409f182e665cbec7dca298aea49af1d1af57944cac9
Timestamp: 1711063886 Timestamp [UCT]: 2024-03-21 23:31:26 Age [y:d:h:m:s]: 01:085:16:21:01
Block: 983491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322133 RingCT/type: yes/0
Extra: 016ebdaaf0fedb6686c3a0d409f182e665cbec7dca298aea49af1d1af57944cac902110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d263c02fb14c680158a6eeff4d1820fd82b5c2497f8583e995ab6cf97f3d120f 0.600000000000 1443630 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": 983501, "vin": [ { "gen": { "height": 983491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d263c02fb14c680158a6eeff4d1820fd82b5c2497f8583e995ab6cf97f3d120f" } } ], "extra": [ 1, 110, 189, 170, 240, 254, 219, 102, 134, 195, 160, 212, 9, 241, 130, 230, 101, 203, 236, 125, 202, 41, 138, 234, 73, 175, 29, 26, 245, 121, 68, 202, 201, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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