Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d552cab043379850d8321e85494e3a7786b7e04e755712a8a6694c1a78641134

Tx prefix hash: f0056051be53890cbe5b85979b2ae62e703270b4148c145f327b4c14cc2ffef9
Tx public key: 74723165a03f0a5a10d53432eb295ff34d0e0a6b2e27361072b2be99b9631121
Timestamp: 1737765390 Timestamp [UCT]: 2025-01-25 00:36:30 Age [y:d:h:m:s]: 00:143:22:27:22
Block: 1204647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102599 RingCT/type: yes/0
Extra: 0174723165a03f0a5a10d53432eb295ff34d0e0a6b2e27361072b2be99b9631121021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68e984e5b65b78d8fd4fc9dd7a1f684ef2c377186a01af79e5c26455982810b0 0.600000000000 1691338 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": 1204657, "vin": [ { "gen": { "height": 1204647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68e984e5b65b78d8fd4fc9dd7a1f684ef2c377186a01af79e5c26455982810b0" } } ], "extra": [ 1, 116, 114, 49, 101, 160, 63, 10, 90, 16, 213, 52, 50, 235, 41, 95, 243, 77, 14, 10, 107, 46, 39, 54, 16, 114, 178, 190, 153, 185, 99, 17, 33, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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