Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8d82a3667f625190ce1b0ca5bcbd7d45d466ff3b521bf7742d6d579ec0f9d33

Tx prefix hash: 6d2f41a7e169f0dc7ac1b7adb649673e03318391bd0e4f8575203e910f20f282
Tx public key: 06293cbcdf965a8a1b927faba24401a9d545b27de4cb6ee44775c8641933b269
Timestamp: 1699075435 Timestamp [UCT]: 2023-11-04 05:23:55 Age [y:d:h:m:s]: 01:175:09:09:24
Block: 884289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386351 RingCT/type: yes/0
Extra: 0106293cbcdf965a8a1b927faba24401a9d545b27de4cb6ee44775c8641933b26902110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.721080022000 dcy

stealth address amount amount idx
00: 7f7cd8be71a3cdd2b1f569c76b31d9f1036cd752f8a42596315657c4bd2d1777 0.721080022000 1340026 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": 884299, "vin": [ { "gen": { "height": 884289 } } ], "vout": [ { "amount": 721080022, "target": { "key": "7f7cd8be71a3cdd2b1f569c76b31d9f1036cd752f8a42596315657c4bd2d1777" } } ], "extra": [ 1, 6, 41, 60, 188, 223, 150, 90, 138, 27, 146, 127, 171, 162, 68, 1, 169, 213, 69, 178, 125, 228, 203, 110, 228, 71, 117, 200, 100, 25, 51, 178, 105, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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