Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1db9f059b968be74da0da5ad40a776704113ca75b22df37e3fb980e09dcb27b9

Tx prefix hash: 673b417d7efa7e0121fa66ced46c98ee90fb7994218f0077e7481650cebed953
Tx public key: b300d015c94d6d1f325e5fb900a542092e637c92e0cd498415501a294b81c80e
Timestamp: 1714168356 Timestamp [UCT]: 2024-04-26 21:52:36 Age [y:d:h:m:s]: 00:323:01:28:40
Block: 1009204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230970 RingCT/type: yes/0
Extra: 01b300d015c94d6d1f325e5fb900a542092e637c92e0cd498415501a294b81c80e02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa94c07e0c30c321716e5912a4cb51d37c1881a09f997b8545de172c44ba73d2 0.600000000000 1470812 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": 1009214, "vin": [ { "gen": { "height": 1009204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa94c07e0c30c321716e5912a4cb51d37c1881a09f997b8545de172c44ba73d2" } } ], "extra": [ 1, 179, 0, 208, 21, 201, 77, 109, 31, 50, 94, 95, 185, 0, 165, 66, 9, 46, 99, 124, 146, 224, 205, 73, 132, 21, 80, 26, 41, 75, 129, 200, 14, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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