Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6b0ad4111c69d1564f57a1f990ad7e440fefc270d4958a891054f04d0d813bd

Tx prefix hash: 7c1f7f4785f8a7b43c1d82bf17a68cf98349ec01c01f27749e8684a8380a8bbe
Tx public key: a7c6947c684c155cdea7a3db41a8b49d121ff0a882b001dcbfb06e3db83e22e7
Timestamp: 1744840194 Timestamp [UCT]: 2025-04-16 21:49:54 Age [y:d:h:m:s]: 00:218:06:28:10
Block: 1262986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153711 RingCT/type: yes/0
Extra: 01a7c6947c684c155cdea7a3db41a8b49d121ff0a882b001dcbfb06e3db83e22e70211000000036c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea879099f93a4bc52d038398cc15967273089bb1da7d79c97a19d50f0fb94655 0.600000000000 1750169 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": 1262996, "vin": [ { "gen": { "height": 1262986 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea879099f93a4bc52d038398cc15967273089bb1da7d79c97a19d50f0fb94655" } } ], "extra": [ 1, 167, 198, 148, 124, 104, 76, 21, 92, 222, 167, 163, 219, 65, 168, 180, 157, 18, 31, 240, 168, 130, 176, 1, 220, 191, 176, 110, 61, 184, 62, 34, 231, 2, 17, 0, 0, 0, 3, 108, 152, 170, 61, 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