Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdbbaea5fe1424b25656c689a884f105261c43b2b8732f7318687408171c0202

Tx prefix hash: 8818bf9921f66a4ca1ac1f34e82081750a59e9fd0db93b91f8bba52e83c6d711
Tx public key: a193c2ede4e7f25be1e69ff8dadc7c8165e538e3d3de8eb47d51ce065bd03bc7
Timestamp: 1748356908 Timestamp [UCT]: 2025-05-27 14:41:48 Age [y:d:h:m:s]: 00:177:07:45:32
Block: 1292111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124419 RingCT/type: yes/0
Extra: 01a193c2ede4e7f25be1e69ff8dadc7c8165e538e3d3de8eb47d51ce065bd03bc7021100000008523560da000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d575fe8958b2382d8cd349d7e0ae189041d08ae95f00044f1e4b5f5337e7d1b4 0.600000000000 1779582 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": 1292121, "vin": [ { "gen": { "height": 1292111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d575fe8958b2382d8cd349d7e0ae189041d08ae95f00044f1e4b5f5337e7d1b4" } } ], "extra": [ 1, 161, 147, 194, 237, 228, 231, 242, 91, 225, 230, 159, 248, 218, 220, 124, 129, 101, 229, 56, 227, 211, 222, 142, 180, 125, 81, 206, 6, 91, 208, 59, 199, 2, 17, 0, 0, 0, 8, 82, 53, 96, 218, 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