Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43839637f17f2653791663f986267f803cf3edc27e99d579fda874a8058a78b7

Tx prefix hash: a51d80c326baf86807def784a56d812c2c817c619d414e1f45c1e68f8d791c3e
Tx public key: c311a298fa425ef2564e5c008a95b563daf5bdccba908bf41fdb9d40c1fb7459
Timestamp: 1750780689 Timestamp [UCT]: 2025-06-24 15:58:09 Age [y:d:h:m:s]: 00:148:16:24:32
Block: 1311916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104198 RingCT/type: yes/0
Extra: 01c311a298fa425ef2564e5c008a95b563daf5bdccba908bf41fdb9d40c1fb7459021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe08cb14bd88afb488153e6029fa915171cd5b3f17ec964b8b149abcac3bc36a 0.600000000000 1799545 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": 1311926, "vin": [ { "gen": { "height": 1311916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe08cb14bd88afb488153e6029fa915171cd5b3f17ec964b8b149abcac3bc36a" } } ], "extra": [ 1, 195, 17, 162, 152, 250, 66, 94, 242, 86, 78, 92, 0, 138, 149, 181, 99, 218, 245, 189, 204, 186, 144, 139, 244, 31, 219, 157, 64, 193, 251, 116, 89, 2, 17, 0, 0, 0, 1, 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