Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da34ffe30d5f5b043cf3215549102921852df5ea4c6936e0b1196798d27c1014

Tx prefix hash: 609c7d41b4a8c0bbd56e93d3ecbfd601b398f62bd477b6b21a1ba288de26b52c
Tx public key: 587c741753d38bdc4ec13dba2cc9f0651872e00ae0350d63b86fc3a75a3db11e
Timestamp: 1737846816 Timestamp [UCT]: 2025-01-25 23:13:36 Age [y:d:h:m:s]: 00:047:16:48:38
Block: 1205315 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33917 RingCT/type: yes/0
Extra: 01587c741753d38bdc4ec13dba2cc9f0651872e00ae0350d63b86fc3a75a3db11e0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cfd53ea2db17148b1a3567867ae23a2576b0987e1e70b4b218501022ce1d2ce 0.600000000000 1692012 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": 1205325, "vin": [ { "gen": { "height": 1205315 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cfd53ea2db17148b1a3567867ae23a2576b0987e1e70b4b218501022ce1d2ce" } } ], "extra": [ 1, 88, 124, 116, 23, 83, 211, 139, 220, 78, 193, 61, 186, 44, 201, 240, 101, 24, 114, 224, 10, 224, 53, 13, 99, 184, 111, 195, 167, 90, 61, 177, 30, 2, 17, 0, 0, 0, 1, 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