Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e088f2bbf89f4f8775687af1440d99bfcf1476a7f0ae1335e76d8a01d208c8e

Tx prefix hash: 590a38b49845c366e36985a25067135737236c76f2542f5f7089dede58c806ea
Tx public key: b4ebe95dae3502f76f63a02411e7bb8316a1b88fdd8cd8718dd83b610cba8e54
Timestamp: 1749481561 Timestamp [UCT]: 2025-06-09 15:06:01 Age [y:d:h:m:s]: 00:158:08:31:05
Block: 1301432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110843 RingCT/type: yes/0
Extra: 01b4ebe95dae3502f76f63a02411e7bb8316a1b88fdd8cd8718dd83b610cba8e54021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2262fc84b7effc55bab3190d2f5e1aae04126a6a2b08f1821d9a94d05bab40c 0.600000000000 1788991 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": 1301442, "vin": [ { "gen": { "height": 1301432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2262fc84b7effc55bab3190d2f5e1aae04126a6a2b08f1821d9a94d05bab40c" } } ], "extra": [ 1, 180, 235, 233, 93, 174, 53, 2, 247, 111, 99, 160, 36, 17, 231, 187, 131, 22, 161, 184, 143, 221, 140, 216, 113, 141, 216, 59, 97, 12, 186, 142, 84, 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