Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ccc5b726675f1b4263a3841086b55f8733470acc0e563f79e1cac74fa3204b4

Tx prefix hash: 1b4559e30edc84c04112d23fdded9102d36760928f16d6cf9accc50a432d7f14
Tx public key: 8b3bd7dfb02820a2f1e9e93fa0f37c0cce86c60b9d185142e477afc501cd5c82
Timestamp: 1746512111 Timestamp [UCT]: 2025-05-06 06:15:11 Age [y:d:h:m:s]: 00:231:16:34:21
Block: 1276825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163339 RingCT/type: yes/0
Extra: 018b3bd7dfb02820a2f1e9e93fa0f37c0cce86c60b9d185142e477afc501cd5c820211000000091f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 257eb023a4c9760638e05d51cf157e114472884454795aa9a0e2c77318e59264 0.600000000000 1764172 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": 1276835, "vin": [ { "gen": { "height": 1276825 } } ], "vout": [ { "amount": 600000000, "target": { "key": "257eb023a4c9760638e05d51cf157e114472884454795aa9a0e2c77318e59264" } } ], "extra": [ 1, 139, 59, 215, 223, 176, 40, 32, 162, 241, 233, 233, 63, 160, 243, 124, 12, 206, 134, 198, 11, 157, 24, 81, 66, 228, 119, 175, 197, 1, 205, 92, 130, 2, 17, 0, 0, 0, 9, 31, 144, 81, 122, 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