Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96884216eb4226466aa6c26356d144fa1ab63cb707f59f556548d4e13fa2682f

Tx prefix hash: c5b371689fcd71389c0609f6e1224e5479115e58097213557ee4cc965d785694
Tx public key: ab3de4660aa73b1b142a7fb7b1d24ea763bd33f4490dc6c4c7a1a329369df1aa
Timestamp: 1724147165 Timestamp [UCT]: 2024-08-20 09:46:05 Age [y:d:h:m:s]: 00:276:13:41:54
Block: 1091946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197560 RingCT/type: yes/0
Extra: 01ab3de4660aa73b1b142a7fb7b1d24ea763bd33f4490dc6c4c7a1a329369df1aa02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41351da0011cae027d578ddc3d39a3dc4370195fd144ed548719b0a98cbbe105 0.600000000000 1566593 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": 1091956, "vin": [ { "gen": { "height": 1091946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41351da0011cae027d578ddc3d39a3dc4370195fd144ed548719b0a98cbbe105" } } ], "extra": [ 1, 171, 61, 228, 102, 10, 167, 59, 27, 20, 42, 127, 183, 177, 210, 78, 167, 99, 189, 51, 244, 73, 13, 198, 196, 199, 161, 163, 41, 54, 157, 241, 170, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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