Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4f503156d95e461ebef975879b90a1995eff6568bfbe5216df5f439a2d339bb

Tx prefix hash: 5e63ba5fc25c9b1f0321cd2b2f2ae4866fe7445cbd411e9f1a1e0e48a5d6693e
Tx public key: 443f0b8e5e2def9cc8951a2229910dba2c9141b8a110cef0a454379db69e24c6
Timestamp: 1723047887 Timestamp [UCT]: 2024-08-07 16:24:47 Age [y:d:h:m:s]: 00:294:11:57:17
Block: 1082823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210415 RingCT/type: yes/0
Extra: 01443f0b8e5e2def9cc8951a2229910dba2c9141b8a110cef0a454379db69e24c6021100000001341001ae000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80df0039bd06968365a2a9cb9dabcfd208b21b9355e313a0013e2d85c2a46827 0.600000000000 1556656 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": 1082833, "vin": [ { "gen": { "height": 1082823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80df0039bd06968365a2a9cb9dabcfd208b21b9355e313a0013e2d85c2a46827" } } ], "extra": [ 1, 68, 63, 11, 142, 94, 45, 239, 156, 200, 149, 26, 34, 41, 145, 13, 186, 44, 145, 65, 184, 161, 16, 206, 240, 164, 84, 55, 157, 182, 158, 36, 198, 2, 17, 0, 0, 0, 1, 52, 16, 1, 174, 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