Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32511113c2081d194c75b6ef744a8cf149dd362c5079e3e8836961b2d31be239

Tx prefix hash: 61b2b97931b1ea9b67bce09d73914711fafb16deaa120fce61fa93468e9cad8b
Tx public key: e9b7a7164d20ad0f021012a6dbc46e21833eff08e6ee19c44238a728a24c1d6e
Timestamp: 1726324203 Timestamp [UCT]: 2024-09-14 14:30:03 Age [y:d:h:m:s]: 00:184:19:27:47
Block: 1109987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131919 RingCT/type: yes/0
Extra: 01e9b7a7164d20ad0f021012a6dbc46e21833eff08e6ee19c44238a728a24c1d6e021100000002e914dd15000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: f8e336f6699be363b40fbc5e7721d455165f0cf84438ea46cc66dbb71c14e518 0.608000000000 1588430 of 0

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": 1109997, "vin": [ { "gen": { "height": 1109987 } } ], "vout": [ { "amount": 608000000, "target": { "key": "f8e336f6699be363b40fbc5e7721d455165f0cf84438ea46cc66dbb71c14e518" } } ], "extra": [ 1, 233, 183, 167, 22, 77, 32, 173, 15, 2, 16, 18, 166, 219, 196, 110, 33, 131, 62, 255, 8, 230, 238, 25, 196, 66, 56, 167, 40, 162, 76, 29, 110, 2, 17, 0, 0, 0, 2, 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