Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6a4744b23595f5bb134ef672993c974b9f649ed001f5e3d2783f5b4eb12d97f

Tx prefix hash: 918e4994c4c34465f70c96de54d2c35dc6e1efc65c4359e412f7a157cd2be824
Tx public key: 8e4cd01fc7f22fddc2338786aa689703a2976ea394e80709080766fdcbcc84e5
Timestamp: 1722329189 Timestamp [UCT]: 2024-07-30 08:46:29 Age [y:d:h:m:s]: 00:238:21:11:56
Block: 1076867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170611 RingCT/type: yes/0
Extra: 018e4cd01fc7f22fddc2338786aa689703a2976ea394e80709080766fdcbcc84e50211000000018c7e50ca000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e5145117b15557bfbbf4555cd44e2f4400ee21e1eb5167dfbdf37a9aabcb1c1 0.600000000000 1549408 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": 1076877, "vin": [ { "gen": { "height": 1076867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e5145117b15557bfbbf4555cd44e2f4400ee21e1eb5167dfbdf37a9aabcb1c1" } } ], "extra": [ 1, 142, 76, 208, 31, 199, 242, 47, 221, 194, 51, 135, 134, 170, 104, 151, 3, 162, 151, 110, 163, 148, 232, 7, 9, 8, 7, 102, 253, 203, 204, 132, 229, 2, 17, 0, 0, 0, 1, 140, 126, 80, 202, 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