Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f03e5b292b29828e37f2dd23600d109eb0fd55579658ca476400e31663c04c0a

Tx prefix hash: d2187be04bc87983f2186fb77c935150b6dc47905638f03de9ef0e3d65367449
Tx public key: 55b28d4bf18326e06ee9d712cdd29c7b02669665c2cf448b8ef9c1c83886d17f
Timestamp: 1735240399 Timestamp [UCT]: 2024-12-26 19:13:19 Age [y:d:h:m:s]: 00:112:13:48:38
Block: 1183779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80256 RingCT/type: yes/0
Extra: 0155b28d4bf18326e06ee9d712cdd29c7b02669665c2cf448b8ef9c1c83886d17f02110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cff9424a25aa479c6f2232b5e1f5dbb6c990fbdbe12a93c8bdae1a82af21bd2 0.600000000000 1670228 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": 1183789, "vin": [ { "gen": { "height": 1183779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cff9424a25aa479c6f2232b5e1f5dbb6c990fbdbe12a93c8bdae1a82af21bd2" } } ], "extra": [ 1, 85, 178, 141, 75, 241, 131, 38, 224, 110, 233, 215, 18, 205, 210, 156, 123, 2, 102, 150, 101, 194, 207, 68, 139, 142, 249, 193, 200, 56, 134, 209, 127, 2, 17, 0, 0, 0, 12, 31, 10, 83, 235, 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