Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32c95b63b04b0f8f33f9d1dacfe54680ae6eb7dd3bff0ccc11f1052cc5afc4fc

Tx prefix hash: 8eee1411154bbfb1147ee7347a77b1cb1cc8d0689286a22415f94e77c566f45c
Tx public key: 44202cdc0d852e542414612cbecc32d4eaf52b46a647d37d503d04c90ad6b136
Timestamp: 1714374466 Timestamp [UCT]: 2024-04-29 07:07:46 Age [y:d:h:m:s]: 01:028:11:45:56
Block: 1010914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281314 RingCT/type: yes/0
Extra: 0144202cdc0d852e542414612cbecc32d4eaf52b46a647d37d503d04c90ad6b13602110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e926d41dc28d0a7e91fa6408e08d42626e79fc9c3128f299f1f431ce1538389 0.600000000000 1472996 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": 1010924, "vin": [ { "gen": { "height": 1010914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e926d41dc28d0a7e91fa6408e08d42626e79fc9c3128f299f1f431ce1538389" } } ], "extra": [ 1, 68, 32, 44, 220, 13, 133, 46, 84, 36, 20, 97, 44, 190, 204, 50, 212, 234, 245, 43, 70, 166, 71, 211, 125, 80, 61, 4, 201, 10, 214, 177, 54, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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