Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8ae6ed2f74669e4259ae2a012f1256b2e7869d8bd425b583205a4af4760e9c7

Tx prefix hash: 95c74d537462b65cd8625691bea520689bff781b7b92f229b1fa4c553be96edf
Tx public key: e80dfc9d0eb98f5ab10489e8635890fc9b55e3b0579dc5bdf34602522a1d2372
Timestamp: 1718141408 Timestamp [UCT]: 2024-06-11 21:30:08 Age [y:d:h:m:s]: 00:264:12:15:18
Block: 1042150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189004 RingCT/type: yes/0
Extra: 01e80dfc9d0eb98f5ab10489e8635890fc9b55e3b0579dc5bdf34602522a1d23720211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2be64acfcf8a5121dd0b82c9a35d45ae0056b98a2b2dd34bc4f6b07541c9fea2 0.600000000000 1510997 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": 1042160, "vin": [ { "gen": { "height": 1042150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2be64acfcf8a5121dd0b82c9a35d45ae0056b98a2b2dd34bc4f6b07541c9fea2" } } ], "extra": [ 1, 232, 13, 252, 157, 14, 185, 143, 90, 177, 4, 137, 232, 99, 88, 144, 252, 155, 85, 227, 176, 87, 157, 197, 189, 243, 70, 2, 82, 42, 29, 35, 114, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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