Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2395f38882976b509a6b693bd1f3d0f3e4c42a5f36c91df44a01b2efaf85fba2

Tx prefix hash: 1a9dfe90fe9dd83b3bca3a23aeca09b2dcbf1e82e64ee6415d7e25568fd512e6
Tx public key: 847d0a5d48551c42e18c1cdaf91e230b6ab9cb676a03ff7100a301369ec22872
Timestamp: 1706702166 Timestamp [UCT]: 2024-01-31 11:56:06 Age [y:d:h:m:s]: 01:068:18:46:38
Block: 947290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310234 RingCT/type: yes/0
Extra: 01847d0a5d48551c42e18c1cdaf91e230b6ab9cb676a03ff7100a301369ec2287202110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50cf503cb12958c86003d44416fa6f1383eea03d8ce2dbd7614267cd1922d403 0.600000000000 1405638 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": 947300, "vin": [ { "gen": { "height": 947290 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50cf503cb12958c86003d44416fa6f1383eea03d8ce2dbd7614267cd1922d403" } } ], "extra": [ 1, 132, 125, 10, 93, 72, 85, 28, 66, 225, 140, 28, 218, 249, 30, 35, 11, 106, 185, 203, 103, 106, 3, 255, 113, 0, 163, 1, 54, 158, 194, 40, 114, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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