Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cb88fb1a10997a55bbacf08f84259d74558a337b83e089322d57bbf610c5788

Tx prefix hash: 270339491068fa4610b3bf8d967d8f8926218c9881db0e9bf21de6698059699f
Tx public key: c63fd472963aaaf86919eee75b3e1bcc35f4d9c4a91d2160d3109e26dc8d8cb3
Timestamp: 1736413655 Timestamp [UCT]: 2025-01-09 09:07:35 Age [y:d:h:m:s]: 00:070:21:20:28
Block: 1193497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50448 RingCT/type: yes/0
Extra: 01c63fd472963aaaf86919eee75b3e1bcc35f4d9c4a91d2160d3109e26dc8d8cb30211000000151f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32adf1045f57be30fcfaf43171eaeb58080b7d166e1de432084ea7c40a9a87ae 0.600000000000 1680058 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": 1193507, "vin": [ { "gen": { "height": 1193497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32adf1045f57be30fcfaf43171eaeb58080b7d166e1de432084ea7c40a9a87ae" } } ], "extra": [ 1, 198, 63, 212, 114, 150, 58, 170, 248, 105, 25, 238, 231, 91, 62, 27, 204, 53, 244, 217, 196, 169, 29, 33, 96, 211, 16, 158, 38, 220, 141, 140, 179, 2, 17, 0, 0, 0, 21, 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