Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8738a246fceb232149e9bafe71b9790d8cf5c025f7c268e228c8a51b59a3b17e

Tx prefix hash: f66c9151c90c0fc5edf065c3ae3b39ce5a7b6cc4dbd07a1e51346f200dd5c98d
Tx public key: 8554945e0319b2bfe28dbea08e08cc11c9b01bd4f5e689f876b8e15e32f9e5a7
Timestamp: 1732370958 Timestamp [UCT]: 2024-11-23 14:09:18 Age [y:d:h:m:s]: 00:352:06:58:38
Block: 1160012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249325 RingCT/type: yes/0
Extra: 018554945e0319b2bfe28dbea08e08cc11c9b01bd4f5e689f876b8e15e32f9e5a70211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3e1dc0e796549bb99a181ae3e801aed24b19576867515cef7f258b4448a82f1 0.600000000000 1645653 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": 1160022, "vin": [ { "gen": { "height": 1160012 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3e1dc0e796549bb99a181ae3e801aed24b19576867515cef7f258b4448a82f1" } } ], "extra": [ 1, 133, 84, 148, 94, 3, 25, 178, 191, 226, 141, 190, 160, 142, 8, 204, 17, 201, 176, 27, 212, 245, 230, 137, 248, 118, 184, 225, 94, 50, 249, 229, 167, 2, 17, 0, 0, 0, 1, 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