Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d46455550c6e326655c58dac0f79c2d726c68ba5370b950aa491b1c5a3000ca

Tx prefix hash: 117cd8a981a80805457e09a7d87050da5bdf33787d8b4713de0db8f6b312da04
Tx public key: 9e04f9d44ceb5b8e4c415181fd38f5a11c9ad01473e3b25d393f277ce2b54730
Timestamp: 1726086947 Timestamp [UCT]: 2024-09-11 20:35:47 Age [y:d:h:m:s]: 00:210:06:54:21
Block: 1108018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150131 RingCT/type: yes/0
Extra: 019e04f9d44ceb5b8e4c415181fd38f5a11c9ad01473e3b25d393f277ce2b5473002110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fa53daee88b7bad7d5368b4106a4173496fdffd70849b073ba53f0649514362 0.600000000000 1585765 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": 1108028, "vin": [ { "gen": { "height": 1108018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fa53daee88b7bad7d5368b4106a4173496fdffd70849b073ba53f0649514362" } } ], "extra": [ 1, 158, 4, 249, 212, 76, 235, 91, 142, 76, 65, 81, 129, 253, 56, 245, 161, 28, 154, 208, 20, 115, 227, 178, 93, 57, 63, 39, 124, 226, 181, 71, 48, 2, 17, 0, 0, 0, 11, 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