Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecbb2c3d1449a5c293608d46b246e8ecfb2f3c920e860b196262397498265ab3

Tx prefix hash: 6fb49ccb8e719ff404d254accdc7743cbefe1beefaee67a7cb71d42c1a99f458
Tx public key: 8c2ff6f169b21e778aad5e137f284105e46e86009796e8049a6e6f1984385c81
Timestamp: 1745140475 Timestamp [UCT]: 2025-04-20 09:14:35 Age [y:d:h:m:s]: 00:207:04:27:44
Block: 1265471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145792 RingCT/type: yes/0
Extra: 018c2ff6f169b21e778aad5e137f284105e46e86009796e8049a6e6f1984385c81021100000005dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26b52dc8b772c928dd9e285d0da4e564fb9f0ce56ac7e44d56c7955ea51d192d 0.600000000000 1752680 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": 1265481, "vin": [ { "gen": { "height": 1265471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26b52dc8b772c928dd9e285d0da4e564fb9f0ce56ac7e44d56c7955ea51d192d" } } ], "extra": [ 1, 140, 47, 246, 241, 105, 178, 30, 119, 138, 173, 94, 19, 127, 40, 65, 5, 228, 110, 134, 0, 151, 150, 232, 4, 154, 110, 111, 25, 132, 56, 92, 129, 2, 17, 0, 0, 0, 5, 219, 181, 113, 193, 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