Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6077319f115ec0ebc86f2b8d33a7ad728f11f1167178466382e67b12eb62f33d

Tx prefix hash: 3107e997ae41b8af7ac4dded8eadb7f68eb8ccc287de3c7b73027b36108d2dc3
Tx public key: 9b0fc0cfdfe66ccef8a6604e25f5a6899faddf4cd32431e871b4002a9135e440
Timestamp: 1743221605 Timestamp [UCT]: 2025-03-29 04:13:25 Age [y:d:h:m:s]: 00:230:19:55:06
Block: 1249579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162714 RingCT/type: yes/0
Extra: 019b0fc0cfdfe66ccef8a6604e25f5a6899faddf4cd32431e871b4002a9135e4400211000000039ba629df000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60e314d049c853b8dedbffe4fc9e9360ab24f7a9328f86dcc5f77b99967c6af1 0.600000000000 1736620 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": 1249589, "vin": [ { "gen": { "height": 1249579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60e314d049c853b8dedbffe4fc9e9360ab24f7a9328f86dcc5f77b99967c6af1" } } ], "extra": [ 1, 155, 15, 192, 207, 223, 230, 108, 206, 248, 166, 96, 78, 37, 245, 166, 137, 159, 173, 223, 76, 211, 36, 49, 232, 113, 180, 0, 42, 145, 53, 228, 64, 2, 17, 0, 0, 0, 3, 155, 166, 41, 223, 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