Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e79f9248892cee90897d567dcebfe25f23ad441910024a56d826c60374cb4270

Tx prefix hash: 3a8db9fbc511272850c96b8b386b85ded943508f0edc0a5e20e9ee1a0e2161c0
Tx public key: 55037c4e7de583158429e2fc08a4426ee90c46cd0bc264a8c157ef0b661307a8
Timestamp: 1703668430 Timestamp [UCT]: 2023-12-27 09:13:50 Age [y:d:h:m:s]: 01:316:22:43:50
Block: 922159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485356 RingCT/type: yes/0
Extra: 0155037c4e7de583158429e2fc08a4426ee90c46cd0bc264a8c157ef0b661307a80211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfef976a55529af12d0bde4837583280795d18e5dc319e2dd5f5c6e3eec6a22d 0.600000000000 1379853 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": 922169, "vin": [ { "gen": { "height": 922159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfef976a55529af12d0bde4837583280795d18e5dc319e2dd5f5c6e3eec6a22d" } } ], "extra": [ 1, 85, 3, 124, 78, 125, 229, 131, 21, 132, 41, 226, 252, 8, 164, 66, 110, 233, 12, 70, 205, 11, 194, 100, 168, 193, 87, 239, 11, 102, 19, 7, 168, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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