Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1abb0a239fda4b286ca51ee1aaf2811b553c6ee15878f023751ce4cf3e428254

Tx prefix hash: e7673b36880a9649e2f76f668cce7d3ac15c3615a345cb3c1286b6e6e1fc4ee4
Tx public key: 821817fe65396da10167eed3ae2bfa39fb529ba1f36f5ee358299f5cff78a2bd
Timestamp: 1746607652 Timestamp [UCT]: 2025-05-07 08:47:32 Age [y:d:h:m:s]: 00:196:22:03:22
Block: 1277619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138447 RingCT/type: yes/0
Extra: 01821817fe65396da10167eed3ae2bfa39fb529ba1f36f5ee358299f5cff78a2bd02110000000c1f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a806aed4ded09f5c00bb0e1f2e9df817ca3cd5d11ea5e36a640ad60afb932a17 0.600000000000 1764976 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": 1277629, "vin": [ { "gen": { "height": 1277619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a806aed4ded09f5c00bb0e1f2e9df817ca3cd5d11ea5e36a640ad60afb932a17" } } ], "extra": [ 1, 130, 24, 23, 254, 101, 57, 109, 161, 1, 103, 238, 211, 174, 43, 250, 57, 251, 82, 155, 161, 243, 111, 94, 227, 88, 41, 159, 92, 255, 120, 162, 189, 2, 17, 0, 0, 0, 12, 31, 144, 81, 122, 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