Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfb89bbe9a3e99ec78b5aabc5b8cb7d6f62ec88e8f529828c7cc2554ef8cd356

Tx prefix hash: d737e531a9a6808930a945ec3d5769be68e5ef0a52cef77d40ce956307afb4f7
Tx public key: 42a0515e9ca4944de39d3e10167544a0cd60547779e9b92e16bd2d16f02fb96b
Timestamp: 1749388238 Timestamp [UCT]: 2025-06-08 13:10:38 Age [y:d:h:m:s]: 00:159:07:29:45
Block: 1300653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111540 RingCT/type: yes/0
Extra: 0142a0515e9ca4944de39d3e10167544a0cd60547779e9b92e16bd2d16f02fb96b021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: baa2632bce493c99ecfc6279494ca339e1e0a79d0b0ddc34e7f093a2c987246e 0.600000000000 1788202 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": 1300663, "vin": [ { "gen": { "height": 1300653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "baa2632bce493c99ecfc6279494ca339e1e0a79d0b0ddc34e7f093a2c987246e" } } ], "extra": [ 1, 66, 160, 81, 94, 156, 164, 148, 77, 227, 157, 62, 16, 22, 117, 68, 160, 205, 96, 84, 119, 121, 233, 185, 46, 22, 189, 45, 22, 240, 47, 185, 107, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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