Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e3d8b743bf031c0cf7da982c10c5f7bc6d33e5d3bdbbfeae90b60cde6393b93

Tx prefix hash: ef609f7daf1f0cf4fa955c8be8f8df5078df7c6c71fc4371ed61706d9dfd9a16
Tx public key: e9555d403bf56a9adb439d1166ba4c0f2480b8b8a8687ff8061540744ea3dc00
Timestamp: 1724408927 Timestamp [UCT]: 2024-08-23 10:28:47 Age [y:d:h:m:s]: 00:216:19:35:47
Block: 1094122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154802 RingCT/type: yes/0
Extra: 01e9555d403bf56a9adb439d1166ba4c0f2480b8b8a8687ff8061540744ea3dc00021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 266b3b515ab737ce86369b0818e95a099b93515fd088a82e9339b78e26112793 0.600000000000 1569203 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": 1094132, "vin": [ { "gen": { "height": 1094122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "266b3b515ab737ce86369b0818e95a099b93515fd088a82e9339b78e26112793" } } ], "extra": [ 1, 233, 85, 93, 64, 59, 245, 106, 154, 219, 67, 157, 17, 102, 186, 76, 15, 36, 128, 184, 184, 168, 104, 127, 248, 6, 21, 64, 116, 78, 163, 220, 0, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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