Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d7c2773062bd96576faa4e055b18d80c88304aac7c67c66f58014c1e39f8afa

Tx prefix hash: c5350f65b3703a4db0ff80ac3bfa221b563d0e5b3463be0adb4ac9ea4feeedf8
Tx public key: bb408d8619cec9b5a726e8b8d13ace3cfed4a8a284a92df6101b2ef4c70f9218
Timestamp: 1725206140 Timestamp [UCT]: 2024-09-01 15:55:40 Age [y:d:h:m:s]: 00:211:02:58:00
Block: 1100718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150735 RingCT/type: yes/0
Extra: 01bb408d8619cec9b5a726e8b8d13ace3cfed4a8a284a92df6101b2ef4c70f9218021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea5a2bf603d419f5054311ddae7f4ee3dd63d8ec81d2e8f840b37e340605a654 0.600000000000 1576697 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": 1100728, "vin": [ { "gen": { "height": 1100718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea5a2bf603d419f5054311ddae7f4ee3dd63d8ec81d2e8f840b37e340605a654" } } ], "extra": [ 1, 187, 64, 141, 134, 25, 206, 201, 181, 167, 38, 232, 184, 209, 58, 206, 60, 254, 212, 168, 162, 132, 169, 45, 246, 16, 27, 46, 244, 199, 15, 146, 24, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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