Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c4fa4325507e55a24c91b95f67ec3aac1d452135c2e6af23f8f0de1b7b467ad

Tx prefix hash: fc778dc2ea3232487f3be3e0d4e845f3d0d50f16c76d1de13b7893af6985d8a8
Tx public key: b33b4b59d6e83e12e249c153535a70b6bd5cc1c38f437fbeced06b8d0279fd77
Timestamp: 1700460519 Timestamp [UCT]: 2023-11-20 06:08:39 Age [y:d:h:m:s]: 01:152:18:55:29
Block: 895559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370367 RingCT/type: yes/0
Extra: 01b33b4b59d6e83e12e249c153535a70b6bd5cc1c38f437fbeced06b8d0279fd770211000000024b8f5122000000000000000000

1 output(s) for total of 0.661669717000 dcy

stealth address amount amount idx
00: 47de03e41b22e1fa1cb422de0dbc8f97c23c678c09c57b4df31100ca3dd92421 0.661669717000 1351796 of 0

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": 895569, "vin": [ { "gen": { "height": 895559 } } ], "vout": [ { "amount": 661669717, "target": { "key": "47de03e41b22e1fa1cb422de0dbc8f97c23c678c09c57b4df31100ca3dd92421" } } ], "extra": [ 1, 179, 59, 75, 89, 214, 232, 62, 18, 226, 73, 193, 83, 83, 90, 112, 182, 189, 92, 193, 195, 143, 67, 127, 190, 206, 208, 107, 141, 2, 121, 253, 119, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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