Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8aefd85f3f135d03789c765f8345ea3eb3114e88d12983af1502ebc73686ad01

Tx prefix hash: 5c1f54e3e5b32c42be4f2a691e25e680a00f46ac5e545725c68a653e852cf36c
Tx public key: 92d7ad7da130fcc1b16f54eb405a3d77ef8c258aefb035a0b00809a1076fa63f
Timestamp: 1735882981 Timestamp [UCT]: 2025-01-03 05:43:01 Age [y:d:h:m:s]: 00:075:04:53:32
Block: 1189111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53537 RingCT/type: yes/0
Extra: 0192d7ad7da130fcc1b16f54eb405a3d77ef8c258aefb035a0b00809a1076fa63f021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76627a3c89cb7a5cc46eaa954db8b17e48c7e552341fc8948a95ed009ab15618 0.600000000000 1675616 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": 1189121, "vin": [ { "gen": { "height": 1189111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76627a3c89cb7a5cc46eaa954db8b17e48c7e552341fc8948a95ed009ab15618" } } ], "extra": [ 1, 146, 215, 173, 125, 161, 48, 252, 193, 177, 111, 84, 235, 64, 90, 61, 119, 239, 140, 37, 138, 239, 176, 53, 160, 176, 8, 9, 161, 7, 111, 166, 63, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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