Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b603c815174d57f6fe8991ae3fadee62e03bec46fe0d26dd761e5d109a0e274e

Tx prefix hash: 7e378e3368d99753d35e28446d0067a7130cafb79c39ef08309b40cf9fc5cba2
Tx public key: 78425ae6257f95241071e2dcabd0aa19e5c7a33076d1d7fcce100e278e8df00b
Timestamp: 1748890378 Timestamp [UCT]: 2025-06-02 18:52:58 Age [y:d:h:m:s]: 00:164:12:25:45
Block: 1296526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115272 RingCT/type: yes/0
Extra: 0178425ae6257f95241071e2dcabd0aa19e5c7a33076d1d7fcce100e278e8df00b02110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ba5b24b1454d81f773626e87a3287f7c3f6d870604e69ffd24676644ec6a239 0.600000000000 1784037 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": 1296536, "vin": [ { "gen": { "height": 1296526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ba5b24b1454d81f773626e87a3287f7c3f6d870604e69ffd24676644ec6a239" } } ], "extra": [ 1, 120, 66, 90, 230, 37, 127, 149, 36, 16, 113, 226, 220, 171, 208, 170, 25, 229, 199, 163, 48, 118, 209, 215, 252, 206, 16, 14, 39, 142, 141, 240, 11, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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