Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c1a92132815df5618f0e88761f1b6d89a56428b04e4cbc83cc573dd818d61a2

Tx prefix hash: 0b6c4dec212199df5b2c8f8a66e250f1c98ef075572f286eb4adc2f6a0ca4bc3
Tx public key: cc82eb809bd8911e07dce0980c90f0d0e96a303b49991d058ca8b7f0e885cb63
Timestamp: 1735795724 Timestamp [UCT]: 2025-01-02 05:28:44 Age [y:d:h:m:s]: 00:155:21:50:53
Block: 1188373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111260 RingCT/type: yes/0
Extra: 01cc82eb809bd8911e07dce0980c90f0d0e96a303b49991d058ca8b7f0e885cb63021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed1d1bef014798400bb7e0c7b49dc6c5ef156227546ec137685077a7c8844c4a 0.600000000000 1674874 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": 1188383, "vin": [ { "gen": { "height": 1188373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed1d1bef014798400bb7e0c7b49dc6c5ef156227546ec137685077a7c8844c4a" } } ], "extra": [ 1, 204, 130, 235, 128, 155, 216, 145, 30, 7, 220, 224, 152, 12, 144, 240, 208, 233, 106, 48, 59, 73, 153, 29, 5, 140, 168, 183, 240, 232, 133, 203, 99, 2, 17, 0, 0, 0, 5, 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