Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d49ff92800829544258476431b68ca30ce0685fd64db368f145003271ca96b9

Tx prefix hash: 039875f5c17224a84ffdb19db9d59dbb8177c229c1570dd4f41ccd52af6a9b8d
Tx public key: 5a2bc791f6281ffc0efdd27c5e185045eba89c2c2fa4eed774a0c3b9b3cd976f
Timestamp: 1720419979 Timestamp [UCT]: 2024-07-08 06:26:19 Age [y:d:h:m:s]: 00:200:17:56:24
Block: 1061042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143596 RingCT/type: yes/0
Extra: 015a2bc791f6281ffc0efdd27c5e185045eba89c2c2fa4eed774a0c3b9b3cd976f02110000000fe914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c76f171758670b8b8b6ef8f970bf7be5128a9337f0f6e6b1584ce6c1dc696d59 0.600000000000 1531533 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": 1061052, "vin": [ { "gen": { "height": 1061042 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c76f171758670b8b8b6ef8f970bf7be5128a9337f0f6e6b1584ce6c1dc696d59" } } ], "extra": [ 1, 90, 43, 199, 145, 246, 40, 31, 252, 14, 253, 210, 124, 94, 24, 80, 69, 235, 168, 156, 44, 47, 164, 238, 215, 116, 160, 195, 185, 179, 205, 151, 111, 2, 17, 0, 0, 0, 15, 233, 20, 221, 21, 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