Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 354cd323277a916563709e96c9da73fbb286100e54dc059ccf477125eee10f9a

Tx prefix hash: c809eeda53a4537a19e187ca7c1f972e869ac3a6b3b6b6b4de2f27b96ecbb042
Tx public key: 7452d5c4c5a5b293a10b1d67cdc313a74c6ee8be2ea561fb48d4ad3281f81d21
Timestamp: 1734339708 Timestamp [UCT]: 2024-12-16 09:01:48 Age [y:d:h:m:s]: 00:093:14:25:22
Block: 1176348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66684 RingCT/type: yes/0
Extra: 017452d5c4c5a5b293a10b1d67cdc313a74c6ee8be2ea561fb48d4ad3281f81d21021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9849385ec5b8c4543ba291297f67f419e5f8f8b4efea3a26af446e3934b21647 0.600000000000 1662679 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": 1176358, "vin": [ { "gen": { "height": 1176348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9849385ec5b8c4543ba291297f67f419e5f8f8b4efea3a26af446e3934b21647" } } ], "extra": [ 1, 116, 82, 213, 196, 197, 165, 178, 147, 161, 11, 29, 103, 205, 195, 19, 167, 76, 110, 232, 190, 46, 165, 97, 251, 72, 212, 173, 50, 129, 248, 29, 33, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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