Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b5d7f7898aa73ec00b6a82522d2d54b642758dfdbe48154de547bdbf6a5ce3c

Tx prefix hash: 6f04f29a9694908cc04b4e19c21934e30a699cb5fecf3b42ab0b80ce9c5a0c5f
Tx public key: 36b264db4b778f471dfac010b48ae607b2cbdb5522578f81fa982b28a0df311f
Timestamp: 1764471480 Timestamp [UCT]: 2025-11-30 02:58:00 Age [y:d:h:m:s]: 00:025:10:41:35
Block: 1423120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18208 RingCT/type: yes/0
Extra: 0136b264db4b778f471dfac010b48ae607b2cbdb5522578f81fa982b28a0df311f02110000000117b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf1b6f46709e097a3da194b01eda3cd33b7ba4398a38bef2acdcfd03a54277b3 0.600000000000 1911723 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": 1423130, "vin": [ { "gen": { "height": 1423120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf1b6f46709e097a3da194b01eda3cd33b7ba4398a38bef2acdcfd03a54277b3" } } ], "extra": [ 1, 54, 178, 100, 219, 75, 119, 143, 71, 29, 250, 192, 16, 180, 138, 230, 7, 178, 203, 219, 85, 34, 87, 143, 129, 250, 152, 43, 40, 160, 223, 49, 31, 2, 17, 0, 0, 0, 1, 23, 177, 145, 50, 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