Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6032d908700c6c7c91ef2c8773ee0976d3882b2a4b1725fa7e5878fb35322df

Tx prefix hash: 3ccb788817741ef5bcb8d04a2091434b5e6987fbbad5f35f76399af7bad39b06
Tx public key: c627084e4996d1274f09ed1caf0cf08d4fa2aad3500fea1c078e0ee916a41c61
Timestamp: 1723545490 Timestamp [UCT]: 2024-08-13 10:38:10 Age [y:d:h:m:s]: 00:237:10:50:27
Block: 1086950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169573 RingCT/type: yes/0
Extra: 01c627084e4996d1274f09ed1caf0cf08d4fa2aad3500fea1c078e0ee916a41c61021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e59b4266a7f3d417f291be5cbe5f14f2a970279b64d645a2916b5bf0679bcde7 0.600000000000 1561549 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": 1086960, "vin": [ { "gen": { "height": 1086950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e59b4266a7f3d417f291be5cbe5f14f2a970279b64d645a2916b5bf0679bcde7" } } ], "extra": [ 1, 198, 39, 8, 78, 73, 150, 209, 39, 79, 9, 237, 28, 175, 12, 240, 141, 79, 162, 170, 211, 80, 15, 234, 28, 7, 142, 14, 233, 22, 164, 28, 97, 2, 17, 0, 0, 0, 3, 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