Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afc46e834d52b4b9e4a33759f81828454d817634a7c81cfe5a4bd9e529b7cf69

Tx prefix hash: 7293466109279b4f282e2f7c60795f50e0d3d999456f198a2e5ff5185765fc46
Tx public key: 41972694b2b9e7f0fa66b4be32a7713a0211805b1d46c90473c9c9912bd65447
Timestamp: 1765746575 Timestamp [UCT]: 2025-12-14 21:09:35 Age [y:d:h:m:s]: 00:024:22:33:31
Block: 1433677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17873 RingCT/type: yes/0
Extra: 0141972694b2b9e7f0fa66b4be32a7713a0211805b1d46c90473c9c9912bd65447021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f2f21cdbb1981877b7a6e3e94fb296f6215d2d12cfbf3b42dea764598edddb9 0.600000000000 1922458 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": 1433687, "vin": [ { "gen": { "height": 1433677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f2f21cdbb1981877b7a6e3e94fb296f6215d2d12cfbf3b42dea764598edddb9" } } ], "extra": [ 1, 65, 151, 38, 148, 178, 185, 231, 240, 250, 102, 180, 190, 50, 167, 113, 58, 2, 17, 128, 91, 29, 70, 201, 4, 115, 201, 201, 145, 43, 214, 84, 71, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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