Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 070a8354eb56b485cdd5e2f3ffabe8c5c236d712a276a9b6014a27af24eb44fe

Tx prefix hash: f0c4e81c1f292f6b6c6827042bb197b000314c66934e877b2f742e1a8ee9eea7
Tx public key: 30a4e3d57dd16f100bcf5f94344972e1d56a8f90cad0f410882e928e76b4fa86
Timestamp: 1735209509 Timestamp [UCT]: 2024-12-26 10:38:29 Age [y:d:h:m:s]: 00:328:03:34:05
Block: 1183533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232038 RingCT/type: yes/0
Extra: 0130a4e3d57dd16f100bcf5f94344972e1d56a8f90cad0f410882e928e76b4fa86021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f95cecbbbcc732fa2eed7abaf9df14e13d1ce5217d049f6b1c026496da9cd7e 0.600000000000 1669978 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": 1183543, "vin": [ { "gen": { "height": 1183533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f95cecbbbcc732fa2eed7abaf9df14e13d1ce5217d049f6b1c026496da9cd7e" } } ], "extra": [ 1, 48, 164, 227, 213, 125, 209, 111, 16, 11, 207, 95, 148, 52, 73, 114, 225, 213, 106, 143, 144, 202, 208, 244, 16, 136, 46, 146, 142, 118, 180, 250, 134, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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