Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98d373818650981156183bddcae5ecfa1ee6b1b59343cdab8cc50f17a9cf25b3

Tx prefix hash: 47c93d29fe08a25ab949ec9ce468dae20fed12c574eb3bd7f4f1a58f0893af49
Tx public key: f8c9f4b43ce7e12001bcbdf4f7d16697aa1fe9693dcc611df57ac312fb16e1ba
Timestamp: 1744115232 Timestamp [UCT]: 2025-04-08 12:27:12 Age [y:d:h:m:s]: 00:182:19:22:50
Block: 1256973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128332 RingCT/type: yes/0
Extra: 01f8c9f4b43ce7e12001bcbdf4f7d16697aa1fe9693dcc611df57ac312fb16e1ba02110000000c6c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b78c1543e9c4242c7fed5d892352c71861b46b08695be997601e8555a75edb9 0.600000000000 1744092 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": 1256983, "vin": [ { "gen": { "height": 1256973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b78c1543e9c4242c7fed5d892352c71861b46b08695be997601e8555a75edb9" } } ], "extra": [ 1, 248, 201, 244, 180, 60, 231, 225, 32, 1, 188, 189, 244, 247, 209, 102, 151, 170, 31, 233, 105, 61, 204, 97, 29, 245, 122, 195, 18, 251, 22, 225, 186, 2, 17, 0, 0, 0, 12, 108, 152, 170, 61, 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