Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa7ffeb7699058001c9a20f3baf3ba65da79c7eee5829b0fb4774051acff62eb

Tx prefix hash: 9e12fb2655abee6167663510488754159f84cfc49d1820e1547a44fd1382b7c5
Tx public key: ecf1ec74d1295a40a0df24393c06fb70fbff1b869afa59e273edd900c829d0ea
Timestamp: 1758598998 Timestamp [UCT]: 2025-09-23 03:43:18 Age [y:d:h:m:s]: 00:052:05:51:06
Block: 1374457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37404 RingCT/type: yes/0
Extra: 01ecf1ec74d1295a40a0df24393c06fb70fbff1b869afa59e273edd900c829d0ea021100000001ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc6f02475a6130dcaa1b8b600e8c2636a15a8e5e3cea9aa354f055e8bd3a3c49 0.600000000000 1862542 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": 1374467, "vin": [ { "gen": { "height": 1374457 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc6f02475a6130dcaa1b8b600e8c2636a15a8e5e3cea9aa354f055e8bd3a3c49" } } ], "extra": [ 1, 236, 241, 236, 116, 209, 41, 90, 64, 160, 223, 36, 57, 60, 6, 251, 112, 251, 255, 27, 134, 154, 250, 89, 226, 115, 237, 217, 0, 200, 41, 208, 234, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 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