Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7e625241b9b6da74f1a5b2aef58a27c2c6696c01f2aaa8ffd58da3082a5a361

Tx prefix hash: 8c4b0d2ffc2b010d89c9794d67aef2c35ac86607f3308e1539f8e1fd0f6a7dd4
Tx public key: 9d5e3ba33b81b04cfca523aedf54987821d9164e4ab88adbc74d35dacc3ea9b0
Timestamp: 1745726639 Timestamp [UCT]: 2025-04-27 04:03:59 Age [y:d:h:m:s]: 00:240:12:50:27
Block: 1270330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169656 RingCT/type: yes/0
Extra: 019d5e3ba33b81b04cfca523aedf54987821d9164e4ab88adbc74d35dacc3ea9b002110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 701259841a97666849a1633a572ad3da2edbd88b832a425ef20a6430c736a7b6 0.600000000000 1757571 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": 1270340, "vin": [ { "gen": { "height": 1270330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "701259841a97666849a1633a572ad3da2edbd88b832a425ef20a6430c736a7b6" } } ], "extra": [ 1, 157, 94, 59, 163, 59, 129, 176, 76, 252, 165, 35, 174, 223, 84, 152, 120, 33, 217, 22, 78, 74, 184, 138, 219, 199, 77, 53, 218, 204, 62, 169, 176, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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