Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f5ff5dd3277608af33ae4b7e963681db6ea43326a1e1e9560a97e4775466c5a

Tx prefix hash: 5a7e269ef2229b070d13d51cda65b2409b9377b5935af56a6b41905dbcf3a46d
Tx public key: 6ea668b806d001f2ef77f7ebc6cb01f59df7d0594b40b447876b3350adf00fad
Timestamp: 1713520206 Timestamp [UCT]: 2024-04-19 09:50:06 Age [y:d:h:m:s]: 00:209:17:28:00
Block: 1003837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150130 RingCT/type: yes/0
Extra: 016ea668b806d001f2ef77f7ebc6cb01f59df7d0594b40b447876b3350adf00fad0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3398c8a0b7d4282809ecfa15f92753342ab78ac44eb4dc3458e3165352b768da 0.600000000000 1464383 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": 1003847, "vin": [ { "gen": { "height": 1003837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3398c8a0b7d4282809ecfa15f92753342ab78ac44eb4dc3458e3165352b768da" } } ], "extra": [ 1, 110, 166, 104, 184, 6, 208, 1, 242, 239, 119, 247, 235, 198, 203, 1, 245, 157, 247, 208, 89, 75, 64, 180, 71, 135, 107, 51, 80, 173, 240, 15, 173, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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