Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b5fd1ec4a226f05c2a1c9696833b5e37b8832d91617be59340871951a1105a8

Tx prefix hash: 1d78a3841af52e47d59715541452e0d732535bed674068a9eea024ea0deabee6
Tx public key: 8d57fbd5d50a4067e88960bcbf2952a64079b55aa3148bfb2994062b277997b4
Timestamp: 1731459554 Timestamp [UCT]: 2024-11-13 00:59:14 Age [y:d:h:m:s]: 00:183:21:17:30
Block: 1152464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131271 RingCT/type: yes/0
Extra: 018d57fbd5d50a4067e88960bcbf2952a64079b55aa3148bfb2994062b277997b40211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a5ed5b2ec78ffd6dc058a9c1ee088274d6b36130bd7eb506bc84a90f7889c26 0.600000000000 1638061 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": 1152474, "vin": [ { "gen": { "height": 1152464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a5ed5b2ec78ffd6dc058a9c1ee088274d6b36130bd7eb506bc84a90f7889c26" } } ], "extra": [ 1, 141, 87, 251, 213, 213, 10, 64, 103, 232, 137, 96, 188, 191, 41, 82, 166, 64, 121, 181, 90, 163, 20, 139, 251, 41, 148, 6, 43, 39, 121, 151, 180, 2, 17, 0, 0, 0, 3, 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