Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddc9f74a82e8e904a395dceba3a04f91c06113d322d0de23bc10f2e48558dfd8

Tx prefix hash: 8d4651707099d65afbb25dd4d67a9db33461ba04caecfa8205e22f2945a9c90f
Tx public key: d36b421d9391bf042d1e3c37fb076f246247485b75d9ec015195aef06b5104fa
Timestamp: 1744735673 Timestamp [UCT]: 2025-04-15 16:47:53 Age [y:d:h:m:s]: 00:023:05:40:46
Block: 1262121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16612 RingCT/type: yes/0
Extra: 01d36b421d9391bf042d1e3c37fb076f246247485b75d9ec015195aef06b5104fa0211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7049d0f3b061942f11c40eb84125285a7a2cefdb8f3838cb4fd8e106581eafd 0.600000000000 1749298 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": 1262131, "vin": [ { "gen": { "height": 1262121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7049d0f3b061942f11c40eb84125285a7a2cefdb8f3838cb4fd8e106581eafd" } } ], "extra": [ 1, 211, 107, 66, 29, 147, 145, 191, 4, 45, 30, 60, 55, 251, 7, 111, 36, 98, 71, 72, 91, 117, 217, 236, 1, 81, 149, 174, 240, 107, 81, 4, 250, 2, 17, 0, 0, 0, 4, 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