Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75cccf1444ed98213527e21d2a44bd51de21900e294e63be8996597a4c612730

Tx prefix hash: 5a3a6676956c7fc674342742ce7df77dcc75adb84b779b4d33de2dc0c8fecfe2
Tx public key: 2c0a3fe5cc057c68d62ca36f23f3ab5fd63d483745255f071a74409bfd7e3b2c
Timestamp: 1729961214 Timestamp [UCT]: 2024-10-26 16:46:54 Age [y:d:h:m:s]: 00:166:09:16:17
Block: 1140104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118713 RingCT/type: yes/0
Extra: 012c0a3fe5cc057c68d62ca36f23f3ab5fd63d483745255f071a74409bfd7e3b2c021100000003a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 020b746666025b66e02b8692a89fca7493f4da20f3c56a31fffaeb3abc32c4dd 0.600000000000 1623897 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": 1140114, "vin": [ { "gen": { "height": 1140104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "020b746666025b66e02b8692a89fca7493f4da20f3c56a31fffaeb3abc32c4dd" } } ], "extra": [ 1, 44, 10, 63, 229, 204, 5, 124, 104, 214, 44, 163, 111, 35, 243, 171, 95, 214, 61, 72, 55, 69, 37, 95, 7, 26, 116, 64, 155, 253, 126, 59, 44, 2, 17, 0, 0, 0, 3, 161, 29, 186, 152, 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